apigee / apigee/apigeetool-node

How to update <HTTPTargetConnection> in Apigee Edge Proxy Dynamically or Runtime?

Open
#214 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
91
Forks
91
PR merge metrics
No merged PRs in 30d

Description

I am deploying some service called MyService on Ec2 and got the ip or url let's say https://myservice.com

Now I want to use this url https://myservice.com in apigee edge runtime,

Let's say, Below is Apigee Edge Proxy Project Structure.

apiproxy
  - policies
    - somepolicy
  - proxies
    - default.xml
  - targets
    - default.xml
  apiproxy.xml

In below xml file from targets/default.xml, I want to replace https://example.com url Dynamically or Runtime with the url (https://myservice.com) which I got when I deployed the Service called MyService on ec2.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TargetEndpoint name="default">
  <PreFlow name="PreFlow">
    <Request/>
    <Response/>
  </PreFlow>
  <Flows/>
  <PostFlow name="PostFlow">
    <Request/>
    <Response/>
  </PostFlow>
  <HTTPTargetConnection>
    <URL>https://example.com</URL>
  </HTTPTargetConnection>
</TargetEndpoint>

Main reason behind updating this url runtime is:

In my network, we are updating urls on daily basis of the services which are deployed on ec2, here for example, it is MyService on ec2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Apigee proxy structure and targets/default.xml, especially the HTTPTargetConnection URL shown in the issue. Determine whether this repository can support replacing that URL at Apigee Edge runtime using the changing EC2 service address; done means a documented, reproducible approach for the MyService deployment scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
api, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.