Skip to content

Tags: connected-web/template-api

Tags

v1.0.2

Toggle v1.0.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #10 from connected-web/feat/api-consumer-outputs

Expose consumer API outputs and validate them post-deploy

v1.0.1

Toggle v1.0.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #9 from connected-web/feat/cweb-package-release-flow

Adopt cweb package deploy flow and parameterize template-api for portable shared-auth deployments

v1.0.1-rc.4

Toggle v1.0.1-rc.4's commit message
Route release packaging and client generation through dev deployment

v1.0.1-rc.3

Toggle v1.0.1-rc.3's commit message
Normalize publish workflow versions to semver

v1.0.1-rc.2

Toggle v1.0.1-rc.2's commit message
Fix release-mode environment and OAuth defaults for client publish

v1.0.1-rc.1

Toggle v1.0.1-rc.1's commit message
Add migration guide for cweb package deployment flow

1.0.0

Toggle 1.0.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add Publish NPM Client workflow and integrate into PR checks (#7)

* Add Publish NPM Client workflow and integrate into PR checks

* Add workflow_call trigger

* Extend permissions

* Fix endpoint

* Update package.json's

* Update @connected-web/openapi-rest-api to 0.6.0

* feat(api): add header-based authorization support and new account config

* docs(api): document header-based auth (connected-web-dev-with-headers) and add example identity JSON

* Fix linting errors

* feat(api/workflows): add header-based auth environment, make subdomain configurable, and add tests

* Add missing subdomain to test

* Use account-configured stackName instead of hardcoded value

* ci(pr-check): clarify CDK API deploy job names to indicate auth method (Cognito, Header-Based)

* Support reusable workflow 'account' input and use local lambda response helper

* fix(ci): base64-encode AWS_ACCOUNT_CONFIG when exporting to GITHUB_ENV

* Set service bucket based on subdomain

* Pass StackParameters into Resources and use config for service bucket name

* refactor(api): remove serviceDataBucketName and stop using explicit S3 bucket name

* tests(api): expect 401 (Unauthorized) for missing/invalid auth-code in getStatus test

* tests(api): add WHBA post-deployment client tests, add npm script, update OpenAPI fixture

* Add header-based auth headers to workflow; bump @connected-web/openapi-rest-api to v0.6.1

* chore(deps): bump @connected-web/openapi-rest-api to 0.6.2

* tests(post-deployment): use allowlisted auth code; expect 403 for unauthorized UUID

* Remove Content-Type/Accept header requirement; use dynamic auth code in tests

* Fix trailing space

* Update @connected-web/openapi-rest-api to 0.6.3

* Fix tests by sending lowercase header values

* Apply linting

* Update to @connected-web/[email protected]

* Replace jest with mocha

* fix: Add postinstall script to fix module resolution issue for CI

- Added fix-module-resolution.sh to handle broken @connected-web/openapi-rest-api package path
- Updated .mocharc.js configuration
- Cleaned up unnecessary dependencies
- All tests now pass in CI environment

* Attempt to fix things again

* Normalize test headers, update test template assets, and remove debug script

* Remove X-Forwarded-For from disallowedHeaders since it's always provided by API Gateway to the Authorizer.