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

[Question] Publishing APIs to same API Management instance #441

Closed
jthipolito opened this issue Dec 7, 2023 · 3 comments
Closed

[Question] Publishing APIs to same API Management instance #441

jthipolito opened this issue Dec 7, 2023 · 3 comments

Comments

@jthipolito
Copy link

Release version

v4.10.3

Question Details

We have an API Management instance for our DEVTEST environment which currently contains the following:

  • API: life-work-api-dev
  • Product: life-work-integration-dev
  • NamedValues: ClientIdDev
  • ...

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:

  • API: life-work-api-sit
  • Product: life-work-integration-sit
  • NamedValues: ClientIdSit
  • ...

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

  1. Create API in API Management
  2. Extract API and its related entities via extractor pipeline
  3. Update config.env.yaml with names of API's to be created in same API Management instance (e.g. life-work-api-sit etc)
  4. Run publisher pipeline
Copy link

github-actions bot commented Dec 7, 2023

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

@jthipolito jthipolito changed the title Publishing APIs to same API Management instance [Question] [Question] Publishing APIs to same API Management instance Dec 7, 2023
@guythetechie
Copy link
Contributor

@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.

  1. Set up my APIM instance with API life-work-api-dev.
  2. Run extractor. I will have a folder called /artifacts/apis/ life-work-api-dev.
  3. Copy the folder and paste it with a new name /artifacts/apis/life-work-api-sit.
  4. When I run the publisher, it will create API life-work-api-sit.

@jthipolito
Copy link
Author

jthipolito commented Jan 9, 2024

@guythetechie Thanks for this. It worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants