We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currenlty if someone runs ansible-navigator to spin up aws-iaas with ghcr.io/cloudera-labs/cldr-runner:aws-latest it will fail at
ghcr.io/cloudera-labs/cldr-runner:aws-latest
This happens since PostgreSQL changed to url for the keys. cloudera-labs/cloudera.cluster@c0b5d85
The text was updated successfully, but these errors were encountered:
I believe this has been fixed with the updates to cldr-runner in cloudera-labs/cldr-runner#81 and in cloudera.cluster in cloudera-labs/cloudera.cluster#188
cldr-runner
cloudera.cluster
Sorry, something went wrong.
No branches or pull requests
Currenlty if someone runs ansible-navigator to spin up aws-iaas with

ghcr.io/cloudera-labs/cldr-runner:aws-latest
it will fail atThis happens since PostgreSQL changed to url for the keys.
cloudera-labs/cloudera.cluster@c0b5d85
The text was updated successfully, but these errors were encountered: