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

EAM API: allow more than one App type instance per Zone #301

Open
gainsley opened this issue Sep 18, 2024 · 0 comments
Open

EAM API: allow more than one App type instance per Zone #301

gainsley opened this issue Sep 18, 2024 · 0 comments
Labels
correction Suggesting corrections of API specification or indicating misalignment with API design guidelines

Comments

@gainsley
Copy link
Collaborator

Problem description

The 409 conflict response option for app instance create indicates

                message: "Application already instantiated in the given
                  Edge Cloud Zone or Edge Cloud Region"

This implies a specific Application can only be instantiated once in a given zone. I don't recall any requirement for this restriction. This restricts several potential use cases:

  • users may want to deploy more than one instance per zone for testing, or HA
  • if we allow AppManifest updates, then users may want to deploy an instance of the updated App alongside an instance deployed with the previous version of the App.

Expected behavior

Allow an App to deployed more than once per zone.

Alternative solution

Additional context

If there is a use case for the system to enforce than an App can be deployed at most once to each zone, then we can add a boolean field such as onePerZone to the AppManifest definition.

@gainsley gainsley added the correction Suggesting corrections of API specification or indicating misalignment with API design guidelines label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correction Suggesting corrections of API specification or indicating misalignment with API design guidelines
Projects
None yet
Development

No branches or pull requests

1 participant