-
Notifications
You must be signed in to change notification settings - Fork 196
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
[Question] Publishing APIs to same API Management instance #441
Comments
|
jthipolito
changed the title
Publishing APIs to same API Management instance [Question]
[Question] Publishing APIs to same API Management instance
Dec 7, 2023
@jthipolito - this is not supported. We use the resource names as keys and expect them to be the same in every APIM instance. Our configuration system allows you to change resource properties, but not their names. To accomplish your goals with ApiOps, I would copy/paste the folders of my extracted resources.
|
@guythetechie Thanks for this. It worked! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release version
v4.10.3
Question Details
We have an API Management instance for our DEVTEST environment which currently contains the following:
I was able to extract this using the extractor pipeline but would now like to publish it to the same API Management instance but with different names for it and its related entities (product, namedValues etc) like this:
Is publishing an API to the same API Management instance possible?
Expected behavior
Able to create another set of API with different env names and config
Actual behavior
Sit objects are not created when publisher pipeline runs config.env.yaml
Reproduction Steps
The text was updated successfully, but these errors were encountered: