You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the problem that you are trying to solve
Add ZMS client GetJWSDomain API calls and store the results in the Athenz Domain Status field
Describe the solution you'd like
Once the changes to the Athenz Domain spec are made, the Athenz syncer will need to make requests to the JWT Domain API endpoint to populate the Athenz Domain custom resource contents. The Athenz Syncer currently has two locations where it is making the ZMS GetSignedDomain calls, during the 1 minute cron and also during the full resync 60 minute cron. The GetJWSDomain ZMS API calls should be introduced right after the GetSignedDomain calls and the response should be stored as part of the Athenz Domain Status field.
This functionality should be introduced as a feature flag in the form of a command line parameter, in order to allow for a migration process from the SignedDomain to the JWS Domain.
Additional context
More context can be found in the previous issue which is also a prerequisite to complete this one.
The text was updated successfully, but these errors were encountered:
Please describe the problem that you are trying to solve
Add ZMS client GetJWSDomain API calls and store the results in the Athenz Domain Status field
Describe the solution you'd like
Once the changes to the Athenz Domain spec are made, the Athenz syncer will need to make requests to the JWT Domain API endpoint to populate the Athenz Domain custom resource contents. The Athenz Syncer currently has two locations where it is making the ZMS GetSignedDomain calls, during the 1 minute cron and also during the full resync 60 minute cron. The GetJWSDomain ZMS API calls should be introduced right after the GetSignedDomain calls and the response should be stored as part of the Athenz Domain Status field.
This functionality should be introduced as a feature flag in the form of a command line parameter, in order to allow for a migration process from the SignedDomain to the JWS Domain.
Additional context
More context can be found in the previous issue which is also a prerequisite to complete this one.
The text was updated successfully, but these errors were encountered: