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

organizations and environments export blocks when environment feature features.SSLInfo.Enforce set #624

Closed
blackrookgeek opened this issue Jan 16, 2025 · 2 comments · Fixed by #625
Assignees

Comments

@blackrookgeek
Copy link

Describe the bug
When using recently added feature to Apigee: features.SSLInfo.Enforce
Ref: https://cloud.google.com/apigee/docs/api-platform/reference/api-proxy-configuration-reference#environment-level-ssl-enforcement

running:
apigeecli organizations export
apigeecli environments export

results in error:
Error: json: cannot unmarshal object into Go struct field Environment.properties of type []env.Property

Version
apigeecli version 2.8.1 date: 2024-12-30T18:10:19Z [commit: dee62e3]

To Reproduce

  1. Add environment flag: features.SSLInfo.Enforce per guide at https://cloud.google.com/apigee/docs/api-platform/reference/api-proxy-configuration-reference#environment-level-ssl-enforcement
  2. execute either export

Expected behavior
Export should recognize this setting and not error.
Given this setting is configured outside of the environment, but is part of the environment's definition, it would be nice if the Import function also set features.SSLInfo.Enforce to match.

Additional context
Nothing to add.

@srinandan srinandan self-assigned this Jan 17, 2025
@srinandan srinandan linked a pull request Jan 17, 2025 that will close this issue
@srinandan
Copy link
Collaborator

Thanks for opening the issue. The bug is not just with that property, it was with any environment property. The PR fixes this issue.

@ssvaidyanathan
Copy link
Collaborator

Fixed in v2.9.0

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 a pull request may close this issue.

3 participants