v1.0.23

updated workflows

v1.0.22

Modified the add / edit portal page script, to default to visible

v1.0.21

Upgrade workflow actions version

v1.0.20

What's Changed

• Feature/bmc 22377 apigee calls expecting an access token cookie by @smuriana in #59
• Feature/bmc 22377 apigee calls expecting an access token cookie by @smuriana in #60

Full Changelog: v1.0.19...v1.0.20

v1.0.19

Feature/bmc 22256 apigee calls expecting an access token cookie (#58)

* changed the way certificates are uploaded.  We are now uploading the certificate and private key as PEM files

* updating upload portal documentation too

---------

Co-authored-by: ryana-ccbill <ryanabl@ccbill.com>

v1.0.18

Added access_token cookie to upload_spec.py. It seems that all of a sudden, apigee is expecting this cookie.

v1.0.17

Changed the way TLS certificates are uploaded.
Instead of taking a PKS12 certificate, the upload_tls and upload_tls_aliases is now taking two arguments

• cf - certificate pem file
• kf - private key pem file

v1.0.16

Upgrade python image version from 3.7 to 3.12

v1.0.15

Add urllib3 package version

v1.0.14

Added the ability to specify a page_size as an argument when invoking upload_portal_documentation.py . By default page_size is set to 100.

This will fix a current issue where only the first 20 APIs are shown when calling the Apigee API if page_size is not specified, possibly resulting in an error when checking if API documentation already exists.