Steven Hawkins
Steven Hawkins
> @shawkins That's sounds right to me. My qualm with that approach is that users who stay on the happy path will have to take two actions to deal with...
> See my comments on the issue I saw your comment, but you may need to further clarify your suggested approach. Are you saying that you don't want any deprecation...
> Maybe the section of the documentation should be deleted. Do you intend to open a PR for this? > I am closing this. Or do you think this should...
@Talkabout are you literally using "${vault.secretid}" or is it something like vault.realm_secretid - with any _ in the realm name or secret id replaced by a double underscore __ -...
Labels are covered by #15395. Annotations are mentioned on that issue, but would likely need separate handling, which this issue could serve as. #23087 allows the deployment to succeed even...
> We add a supported field to the RealmImport CR but we don't officially support setting env vars on the Deployment/import Job (pod template is not considered supported) You can...
> Something like: Is this the only system property / env variables used by import? If not, it may make sense to instead keep a placeholder flag and a dedicated...
@stustison after some more internal discussion, we'd like to move forward with the proposal above from @vmuzikar - unfortunately it adds a bit more complexity. The closest match for this...
I'm rerunning the failed tests - if they fail again we'll need to look into it more. There have been some intermittent flakiness with import, but the local here are...
Closing in favor of #31232