pulling dependencies from master

[theishshah]

Bug Report

What did you do?
A clear and concise description of the steps you took (or insert a code snippet).

TravisCI runs are fetching master versions of Ansible Molecule (and possibly other dependencies) and as a result a breaking change on a dependency can break the sdk. Note that this specific instance of the issue has been fixed in #1131

What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).

Travis passing when no breaking changes are made in the sdk.

What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).

Travis failed on master with no changes in our repo.

Environment

• operator-sdk version: 0.5.0

Possible Solution

I suggest freezing our dependencies on the latest releases and then updating those versions whenever we lock the new version of the sdk.

[estroz]

@shawn-hurley @fabianvf thoughts?

[shawn-hurley]

yep, I totally agree we should, and will, but we actually need a change in molecule that is unreleased (which is going to be released soon). This means that for now, we need to do it this way, we are tracking this and will be making the necessary changes once molecule is released.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.