Skip to content
New issue

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

Used namespacedSecrets endpoint to get/update rancher secrets in ingest #1107

Merged
merged 1 commit into from
Jan 9, 2024

Conversation

pkalita-lbl
Copy link
Collaborator

Just a quick revision to #1103. I had been testing that locally against the "development" project (which we don't really use anymore). This updates the ingest CLI to use the correct endpoint for the "production" project where we used namespaced secrets.

Copy link
Collaborator

@naglepuff naglepuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I do have one question:

What are the odds we switch away from using namespaced secrets in the future? Coming back here to edit that seems like it could be tedious. Do you think its worth using an environment variable to handle the "secrets" vs. "namespacedSecrets" segment of the URL?

@pkalita-lbl
Copy link
Collaborator Author

Fair question. I don't think that's likely, but that's just based on vibes not any Rancher expertise. Maybe if it needs to be updated in the future we could switch to passing in full endpoints (e.g. /project/xxxxx/someObject/yyyyy) in the environment variables.

@pkalita-lbl pkalita-lbl merged commit 8679de5 into main Jan 9, 2024
2 checks passed
@pkalita-lbl pkalita-lbl deleted the issue-1079-fix-secret-url branch January 9, 2024 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants