-
Notifications
You must be signed in to change notification settings - Fork 233
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
Update to v7.x.x gives warning that domain does not exist #572
Comments
Hi @chris It looks like the ApiGateway Custom Domain is not created. Have you run the |
@rddimon The domain exists - the service has been deployed and using this domain for 3 years. The only change made here is updating the |
@chris hmm then it might be related to the wrong region Is the region specified under the |
@rddimon yes, the region is set in the I will see if I can try pulling down the source and using the plugin from source and doing some debugging to see exactly where/what is triggering the alert. If you have any guidance on at least setting up using the plugin from a local copy/source, that'd be helpful (I didn't see that in the GitHub info, but maybe it's fairly standard (I don't do a lot of JavaScript, so not familiar with how to set that up). |
You will need to run |
Ok, maybe some insight, although I'd think this would affect nearly anyone and thus would be a much bigger problem. It may have to do with the profile/credentials. I noticed that no credentials are provided to the When I use 7.0.2, and I log the actual error message from AWS for this, I get: So, I made the smallest test program I could to try things out, and indeed, if I don't specify credentials, this is the error I get. If I do specify credentials, then it properly returns the domain. Here is the test program I'm using: import { APIGatewayClient, ainNameCommand } from "@aws-sdk/-api-gateway";
import { fromIni } from "@aws-sdk/tial-providers";
async function testIt() {
const credentials = fromIni({profile: mycustom-admin-dev'});
const client = new APIGatewayClient({credentials: credentials, region: 'us-east-2'});
const command = new GetDomainNameCommand({ domainName: "api.mycustom-test.io" });
const response = await client.send(command);
console.log(`response: ${JSON.stringify(response)}`);
}
testIt() Here's the case with failure (i.e. if I don't include the
When I specify the credentials, then the success response is the following (I obscured a few values):
|
Thank you for the investigation! In version In the new AWS SDK V3 I haven't found alternatives The Very helpful work, thank you! |
Hi @chris Will you be able to try the latest version and let us know the result? |
I've updated to 7.0.3, and this does indeed seem to fix things. No more errors/alerts, and my deploy seems to be correct. Thanks for the fix! |
using v7.0.4, same set up as @chris and i am getting the same warning and the custom domain is deploying a new API gateway endpoint rather than linking to the existing API gateway resource config:
|
Community Note
Support Question
Question
When I update to serverless-domain-manager version 7.x (from 6.4.4), I now get a warning that says my domain does not exist. Specifically I see:
This is for an existing/deployed service (for a couple years now). I am using Serverless framework 3.30.1, running on macOS.
It concerns me that it doesn't think my domain exists? Yet it obviously does, and this only gets printed with v7 of the plugin, any prior version did not show this warning, and my custom domain is working fine. I have not done a deploy with v7 as this makes me nervous that something will be broken with this version (so I don't know if a deploy would somehow fix this, etc.).
Command Run
sls info
Console Output
(Note, I've substituted "mycustom" for the name of my actual domain.)
❯ sls info Warning: V1 - 'api.mycustom-test.io' does not exist. service: mycustom-api stage: dev region: us-east-2 stack: mycustom-api-dev endpoints: GET - https://abc12ab123.execute-api.us-east-2.amazonaws.com/dev/mycustom GET - https://abc12ab123.execute-api.us-east-2.amazonaws.com/dev/mycustom/widget functions: mycustom: mycustom-api-dev-mycustom mycustomWidget: mycustom-api-dev-mycustomWidget
Domain Manager Configuration
Replace this with your own
serverless.yml
file (anonymized, of course) to help us better resolve your issue.Versions
Additional context/Screenshots
The text was updated successfully, but these errors were encountered: