knennigtri/aep-tag-tool

Quickly export AEP tag properties to import into other organizations

aep-tag-tool's Issues

Tool fails if there are no rules

Update success message

change:

Prod Library embed code:

<script src='https://assets.adobedtm.com/5e95f0b89f40/549101eb1e87/launch-953251c01f83.min.js' async></script>

to:

Prod Library embed script:
https://assets.adobedtm.com/5e95f0b89f40/549101eb1e87/launch-953251c01f83.min.js

Adobe Auth

Ideally, I'd like to authenticate via NPM with a users credentials, then auto-create an app with Launch API permissions and then either create a postman environment file based on the values.

https://www.npmjs.com/package/@adobe/aio-cli?activeTab=readme
https://www.npmjs.com/package/@adobe/aio-cli-plugin-auth/v/2.4.0
https://www.npmjs.com/package/@adobe/aio-cli-plugin-app#aio-app-create-path

--generate

Auto generates a file to fill out with credentials

--generate -e name-of-my-file.json
--generate -g name-of-my-file.json

Support json from Adobe IO projects

Create a new AIO Project

• Optional Project JSON output
• JWT JSON output
• postman environment json output

Support publish to dev only

Publish library to dev only. This will allow everything to be installed and then published into dev, then any manual configurations can occur and the library can be tested and then published to prod manually.

Target rule requires unique url with adobeaemcloud.com

yml config include globals

Globals:
  SETTINGS_EXT_adobe-target-v2:
    clientCode: xyz
    serverDomain: xyz
    imsOrgId: xyz
  SETTINGS_EXT_adobe-analytics:
    development: xyz
    staging: xzy
    production: xzy
    company: xyz 
    orgId: xyz
    trackingServer
    trackingServerSecure
  SETTINGS_EXT_adobe-mcid
    orgId: xyz

Expand config.yml to support 1+ imports

---
auth:
 CLIENT_ID: xxxxx
 CLIENT_SECRET: xxxxx
 ORG_ID: xxxxx@AdobeOrg
 TECHNICAL_ACCOUNT: [email protected]
 PRIVATE_KEY: ./private.key
imports: [
  ./propertyOne.json,
  ./propertyTwo.json
]
---

OR

---
auth:
 CLIENT_ID: xxxxx
 CLIENT_SECRET: xxxxx
 ORG_ID: xxxxx@AdobeOrg
 TECHNICAL_ACCOUNT: [email protected]
 PRIVATE_KEY: ./private.key
imports: ./propertyOne.json
---

yaml config file for env

Rather than asking a user to manually create the env file and globals file, create a simple yaml file that can extract the values and input them into the postman files.... removing the need to understand postman... and opening the door for less dependency on postman

-o param should auto create the directory if it DNE

move ./newman folder to ./bin/newman

Update to use oAuth

https://developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAuthentication/migration/#step-1-add-the-new-credential-to-your-project