nerdguru / sls-pypi Goto Github PK

You can't use "my" and you can't use a name already used by someone else

Intermittently, the download phase of the publishing process will see the following:

Error processing Readme.md [Errno 2] No such file or directory: '/tmp/samples201/Readme.md'

Not clear why that and .gitignore suffer from this and the others don't. The publish continues, but issues a warning.

Per https://forum.serverless.com/t/serverless-sdk-get-user-handler-module-has-no-attribute/9659

Turning on monitoring for some reason chokes on the current name. Too short? Unclear but changing the name of the function, it's file, and the underlying method fix it.

Result should take in a base domain name and a Hosted Zone ID and combine functionality from the two sources

At the end of installation instruction 4b, there's a snippet that reads:

For the Authorization callback URL, use the value of the domain set in step 4a as the base URL followed by /oauth2/idpresponse, so /oauth2/idpresponse

Only, 4a no longer automatically sets up the UserPoolDomain, it has to be done manually.

Currently the publish process is synchronous, which means it is subject to the API Gateway 30 second execution cap, all for downloading, building, and pushing bits. Early tests with trivial packages show this works fine, but for more sophisticated packages, that might not be the case.

Course correction of prior work should be incorporated here. Should happen after #3

Same as the list.py, but for generating the package page

Specifically, the ARNS for two Lambdas:

• USER_POOL_DOMAIN
• USER_POOL_CLIENT_SETTINGS

Related to #40 for versioning, the Athena query needs to be .lower()

Extending:

https://github.com/novemberfiveco/s3pypi/blob/master/cloudformation/s3-pypi.json

Given some stale arns on my dev account, I had to manually fix the trigger on dynamoPackages to point to the right arn. This may solve itself when installing on a new account.

writeWebLogs is supposed to get triggered when the Athena query drops a new .csv file in the query results bucket:

    events:
      - s3:
          bucket: ${self:provider.custom.QUERY_RESULTS_BUCKET_NAME}
          event: s3:ObjectCreated:*
          rules:
            - suffix: .csv
          existing: true

But the trigger doesn't automatically get set with an sls deploy, instead had to set the trigger manually.

Create a single CloudFormation or Serverless installer for the custom CloudFormation features of these two:

https://github.com/binxio/cfn-certificate-provider
https://github.com/rosberglinhares/CloudFormationCognitoCustomResources

Needed for reporting