-
Notifications
You must be signed in to change notification settings - Fork 72
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
fix: update terms spec url #1291
Conversation
@@ -5,7 +5,7 @@ SHELL = bash | |||
RHOAS_VERSION ?= "dev" | |||
REPOSITORY_OWNER ?= "redhat-developer" | |||
REPOSITORY_NAME ?= "app-services-cli" | |||
TERMS_SPEC_URL ?= "https://raw.githubusercontent.com/redhat-developer/app-services-ui/main/static/configs/terms-conditions-spec.json" | |||
TERMS_SPEC_URL ?= "https://console.redhat.com/apps/application-services/terms-conditions-spec.json" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will probably want a different one for stage and prod?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why we would need it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spec file could be different between stage and prod versions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not have ability to detect env and we need more sophisticated remote config for massso. I think this requirement would need more design etc.
If we need config agains stage I think we should build different version of cli for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this tc config should be refactored to more generic config. Created issue to cover this work but this is out of scope of current PR
Use production based json file.
use termsandconditions file for verification