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

Activate fails with certEnrollmentId error #74

Open
nick-s-morgan opened this issue Dec 10, 2021 · 0 comments
Open

Activate fails with certEnrollmentId error #74

nick-s-morgan opened this issue Dec 10, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@nick-s-morgan
Copy link

nick-s-morgan commented Dec 10, 2021

I am automating the changes to a property using the following flow:

  • akamai property-manager import -p
  • making changes locally (adding a snippet to a rule)
  • akamai property-manager activate -n staging -p

The activate step fails with the following error:

    {
        "message": "Need 'certEnrollmentId' of hostname in order to create secure edge hostname",
        "messageId": "missing_certEnrollmentId",
        "edgehostname": "**.*******.****.com.edgekey.net"
    }

I can see it is failing on the save part of the activation following the merge (which completes with no errors noted). I don't understand why it's trying to create a secure edge hostname. I just want to update an existing property and activate to staging.

I can manually go into ACC and activate the updated property version with no issues.

For reference, the hostnames.json looks to have the following format:

[
    {
        "cnameType": "EDGE_HOSTNAME",
        "cnameFrom": "****-******-******.****.com",
        "cnameTo": "**.*******.****.com.edgekey.net",
        "certProvisioningType": "CPS_MANAGED"
    }
]

For further reference, the output of the merge steps looks as follows:

├──────────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│"validation performed"│"yes"                                                                          │
├──────────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│"validation warnings" │"yes"                                                                          │
├──────────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│"validation errors"   │"no"                                                                           │
├──────────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│"hostname warnings"   │"no"                                                                           │
├──────────────────────┼───────────────────────────────────────────────────────────────────────────────┤
│"hostname errors"     │"no"                                                                           │
└──────────────────────┴───────────────────────────────────────────────────────────────────────────────┘
@lkowalsk-akamai-com lkowalsk-akamai-com added the bug Something isn't working label May 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants