Skip to content
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

43 Deployment #44

Merged
merged 34 commits into from
Apr 16, 2019
Merged

43 Deployment #44

merged 34 commits into from
Apr 16, 2019

Conversation

lojzatran
Copy link
Contributor

Fixes: #43

@lojzatran lojzatran requested a review from LEQADA March 28, 2019 09:36
path: ''


readinessProbe:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have a TODO for that?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#50

} catch (e) {
console.error('Error when creating interface interaction custom type, skipping...', JSON.stringify(e))
logger.error('Error when creating interface interaction custom type, skipping...', JSON.stringify(e))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not stringify an error. Proper format with bunyan would be:
logger.error(e, "My custom message")

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also check al other places in the code.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

await ctpClient.create(ctpClient.builder.types, paymentCustomType)
logger.info('Successfully created payment custom type')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the logger also outputs the tenant info?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now we don't have multitenancy support, so it doesn't have tenant info.

@@ -0,0 +1,13 @@
FROM mhart/alpine-node:10
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just an info: GCP functions support currently only following node versions: 6, 8

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

# memory: '1Gi' #equivalent to 2GiB
# limits:
# cpu: '300m' #30% of CPU time on 1 GCP Core
# memory: '1Gi' #equivalent to 2GB
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why no resources requests/limits are set?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are in a faze of figuring it out 🙂

},
"required": true,
"type": {
"name": "String"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is also date/time type. Is String on purpose here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if (body.results.length === 0) {
logger.debug('Creating interface interaction')
await ctpClient.create(ctpClient.builder.types, interfaceInteractionType)
logger.info('Successfully created an interfaceInteraction type')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would output the key of the type too

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As stated above, I would change it in a different task: #8

@LEQADA LEQADA requested review from ahmetoz and removed request for ahmetoz April 4, 2019 09:30
break
} catch (err) {
} catch (e) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pls add a test for this catch error case.

Copy link
Contributor

@LEQADA LEQADA Apr 9, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is a test and it was failing. Fixed the issue. Thanks

@lojzatran lojzatran marked this pull request as ready for review April 16, 2019 15:09
Copy link
Contributor

@LEQADA LEQADA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GJ 👍

@lojzatran lojzatran merged commit 598d8ba into master Apr 16, 2019
@lojzatran lojzatran deleted the deployment branch April 16, 2019 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create example deployment to production
3 participants