Draft
Conversation
❌MegaLinter analysis: Error
Detailed Issues❌ SPELL / lychee - 1 errorSee detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
ideaship
added a commit
to osism/testbed
that referenced
this pull request
Apr 8, 2026
The deployment guide now exclusively recommends application credentials (osism/osism.github.io#972), where the secret is already contained in clouds.yaml. The secure.yaml file was only needed for username/password auth to separate the password from clouds.yaml. Remove the secure.yaml existence check from setup-testbed.py and delete terraform/secure.yaml.sample. The check was already non-fatal (warning + sleep, no exit) — a compromise from PR #1879 where it was noted that secure.yaml is optional for app credentials. A TODO to add smarter detection was left but never followed up on. For production deployments, a more fine-grained check that validates credentials based on auth type (app credentials vs. username/password) would still be valuable. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ideaship
added a commit
to osism/testbed
that referenced
this pull request
Apr 8, 2026
Users following the deployment guide see the warning "There is no file terraform/secure.yaml, create one by using terraform/secure.yaml.sample as template" in their log output. This is confusing because the guide recommends application credentials, where the secret is already in clouds.yaml and no secure.yaml is needed. Remove the secure.yaml existence check from setup-testbed.py and delete terraform/secure.yaml.sample. The check was already non-fatal (warning + sleep, no exit) — a compromise from PR #1879 where it was noted that secure.yaml is optional for app credentials. A TODO to add smarter detection was left but never followed up on. The deployment guide now exclusively recommends application credentials (osism/osism.github.io#972). For production deployments, a more fine-grained check that validates credentials based on auth type would still be valuable. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ideaship
added a commit
to osism/testbed
that referenced
this pull request
Apr 8, 2026
Users following the deployment guide see the warning "There is no file terraform/secure.yaml, create one by using terraform/secure.yaml.sample as template" in their log output. This is confusing because the guide recommends application credentials, where the secret is already in clouds.yaml and no secure.yaml is needed. Remove the secure.yaml existence check from setup-testbed.py and delete terraform/secure.yaml.sample. The check was already non-fatal (warning + sleep, no exit) — a compromise from PR #1879 where it was noted that secure.yaml is optional for app credentials. A TODO to add smarter detection was left but never followed up on. The deployment guide now exclusively recommends application credentials (osism/osism.github.io#972). For production deployments, a more fine-grained check that validates credentials based on auth type would still be valuable. AI-assisted: Claude Code Signed-off-by: Roger Luethi <luethi@osism.tech>
Rewrite step 3 ("Configure your cloud access profile") of the
testbed deployment guide to provide a single fast path using
application credentials downloaded from Horizon.
The old version had several problems (see issue #960):
clouds-public.yaml was mentioned without context, there was no
guidance on application credential settings, no fast path for
cloud access configuration, and it was unclear what credentials
a provider actually supplies. The section tried to cover
different cases (app credentials vs username/password,
secure.yaml, profiles, cloud naming constraints) without
offering a simple straight path.
Investigation showed that the downloaded clouds.yaml from
Horizon already contains auth_url, region_name, and
identity_api_version — all the information that
clouds-public.yaml provides via the profile parameter. The
only extra field in clouds-public.yaml is image_format (for
4 providers), but Terraform does not use it. Default app
credential settings (empty roles, Unrestricted=false) are
sufficient, confirmed by a successful deployment.
The rewrite removes the username/password alternative (no
clouds.yaml download available from Horizon, requiring manual
YAML construction), the clouds-public.yaml/profile explanation,
and the secure.yaml option. What remains is a linear set of
concrete steps: create app credential in Horizon, download
clouds.yaml, rename the cloud entry, and copy the file.
Closes: #960
AI-assisted: Claude Code
Signed-off-by: Roger Luethi <luethi@osism.tech>
a82e59f to
6ee5aad
Compare
ideaship
added a commit
to osism/testbed
that referenced
this pull request
Apr 9, 2026
Users following the deployment guide see the warning "There is no file terraform/secure.yaml, create one by using terraform/secure.yaml.sample as template" in their log output. This is confusing because the guide recommends application credentials, where the secret is already in clouds.yaml and no secure.yaml is needed. Remove the secure.yaml existence check from setup-testbed.py and delete terraform/secure.yaml.sample. The check was already non-fatal (warning + sleep, no exit) — a compromise from PR #1879 where it was noted that secure.yaml is optional for app credentials. A TODO to add smarter detection was left but never followed up on. The deployment guide now exclusively recommends application credentials (osism/osism.github.io#972). For production deployments, a more fine-grained check that validates credentials based on auth type would still be valuable. AI-assisted: Claude Code Signed-off-by: Roger Luethi <luethi@osism.tech>
ideaship
added a commit
to osism/testbed
that referenced
this pull request
Apr 10, 2026
Users following the deployment guide see the warning "There is no file terraform/secure.yaml, create one by using terraform/secure.yaml.sample as template" in their log output. This is confusing because the guide recommends application credentials, where the secret is already in clouds.yaml and no secure.yaml is needed. Remove the secure.yaml existence check from setup-testbed.py and delete terraform/secure.yaml.sample. The check was already non-fatal (warning + sleep, no exit) — a compromise from PR #1879 where it was noted that secure.yaml is optional for app credentials. A TODO to add smarter detection was left but never followed up on. The deployment guide now exclusively recommends application credentials (osism/osism.github.io#972). For production deployments, a more fine-grained check that validates credentials based on auth type would still be valuable. AI-assisted: Claude Code Signed-off-by: Roger Luethi <luethi@osism.tech>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Rewrite step 3 ("Configure your cloud access profile") of the testbed deployment guide to provide a single fast path using application credentials downloaded from Horizon.
The old version had several problems (see issue #960): clouds-public.yaml was mentioned without context, there was no guidance on application credential settings, no fast path for cloud access configuration, and it was unclear what credentials a provider actually supplies. The section tried to cover different cases (app credentials vs username/password, secure.yaml, profiles, cloud naming constraints) without offering a simple straight path.
Investigation showed that the downloaded clouds.yaml from Horizon already contains auth_url, region_name, and identity_api_version — all the information that
clouds-public.yaml provides via the profile parameter. The only extra field in clouds-public.yaml is image_format (for 4 providers), but Terraform does not use it. Default app credential settings (empty roles, Unrestricted=false) are sufficient, confirmed by a successful deployment.
The rewrite removes the username/password alternative (no clouds.yaml download available from Horizon, requiring manual YAML construction), the clouds-public.yaml/profile explanation, and the secure.yaml option. What remains is a linear set of concrete steps: create app credential in Horizon, download clouds.yaml, rename the cloud entry, and copy the file.
Closes: #960
AI-assisted: Claude Code