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

Specify a default plan #141

Closed
m-mohr opened this issue Oct 24, 2018 · 1 comment
Closed

Specify a default plan #141

m-mohr opened this issue Oct 24, 2018 · 1 comment

Comments

@m-mohr
Copy link
Member

m-mohr commented Oct 24, 2018

For billing, we should allow to specify a default plan. This is important as we need to choose a plan to use for billing once a job or service is created. The user needs to be aware which plan is used otherwise the plan could just change without notice and the user feels betrayed. Therefore the spec should make clear that once a job or service is started the default plan will be set until changed by the user.

@m-mohr m-mohr modified the milestones: v0.4, v0.3.1 Oct 24, 2018
m-mohr added a commit that referenced this issue Oct 26, 2018
- Default billing plan in capabilities (fixing #141)
- Several optional fields such as `output`, `title` and `description` are now nullable instead of requiring to omit them
- The output format is not required in `/preview` any more and thus allows falling back to the default
- Deprecated `eo:resolution` in collection bands is a duplicate of `eo:gsd`. Use `eo:gsd` instead
- Added more error messages
- Other improvements
@m-mohr
Copy link
Member Author

m-mohr commented Oct 26, 2018

Fixed by the referenced commit.

@m-mohr m-mohr closed this as completed Oct 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant