https://serverless-stack.com/ logo
Join Slack
Powered by
I am having trouble with Seed.run deploying my Swa...
# seed
m
I am having trouble with Seed.run deploying my Swagger Stack. Its constantly showing the outdated version of the swagger.yml file, while I have tested the app locally and it works as it should. I should probably post this as well here, to show that the Seed.run is actually "building" my swagger before deploying it.
f
Hey @Meris Tarhanis, what does your Swagger Stack look like?
m
Copy code
import * as sst from '@serverless-stack/resources';

export default class SwaggerStack extends sst.Stack {
  constructor(scope, id, props) {
    super(scope, id, props);

    // Define our Swagger UI App
    const site = new sst.ReactStaticSite(this, 'SwaggerUI', {
      path: 'api-docs',
    });

    // Show the url in the output
    this.addOutputs({
      SiteUrl: site.url,
      ApiOwner: "ProdataHub"
    });
  }
}
Its on a project where we are using older version of SST @Frank
f
I see. And you r seeing that the swagger file doesn’t get built when u run 
sst build
locally, and it’s only getting build when deployed through Seed?
m
I didn't run sst build localy, because I need to be run via Seed.run. But when I did run sst start localy, the swagger frontend would diplay the correct swagger file (the updated one that is inside the project). But when it gets built via the Seed the url link for Swagger frontend is displaying the old version of swagger file.
f
can you try running running 
sst build
or 
sst deploy
locally and see if that happen?
Seed is really just running 
sst deploy
with a couple of extra environment variables ie. 
CI=true
I have a feeling you’d get the same result running it locally.
Open in Slack
PreviousNext
Powered by